5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
- Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-2: Getting Started

Introduction to Process Concepts


The APPX process facility recognizes nine process types: menu, input, output, query, subroutine, update, job, status and inquiry. Each represents a specific kind of activity, and each is comprised of a subset of the structural components (PCFs, frames, and event points, for example) that were described in the previous chapter. However, while the structural components are essentially the same from type to type, the way these components are used to perform a required activity varies. For example, menu and inputprocesses use images toformat the screens that display to a user. Output processes, on the other hand, generally use images to format hard copy, such as a list or report. And subroutine processes do not display information to a user, so no images are required.

Because of such differences, there are a number of concepts that apply to one or more, but not all, process types in APPX. To continue the previous example, the way you position images on a frame has obvious significance to a menu, input, or output process, but no relevance at all to a subroutine. To carry the example even further, there are subtle differences between image positioning for input and output images, because the former display on the screen, while the latter generally print on hard copy. The material that follows discusses a number of these process-specific concepts in detail.

Application Design Manual                                         "Powered by Appx Software"

258

©2006 By APPX Software, Inc. All Rights Reserved